when end user uses VPN, they can access almost everything except the network drives, actually I shall say they can still access the network drives if they know the network path and know how to do the drive mapping. but the thing is not all of them have this issue, some of them can still access those drives by simply open "computer", and those drives are all there. we got the temporary resolution: got users run the logon script after VPN, but they want everything to be as simple as possible. and I don't understand why some of them have the problem while some of them don't either? how can we make it stable? thanks.

Hi, Thanks for posting in Microsoft TechNet forums. It is a name resolution problem. WINS Server default Netbios name resolution does not use hosts file, but lmhosts instead. Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

sorry, I don't get your point, so is there way that users can SEE their network drivers when they are using VPN in Vista? thanks.

Hi, A WINS server is required to map a drive on the Microsoft network. It is more Server side involved as some clients and see but some can't. Consider these suggestions when you try to determine the root of the problem. Issue the net use CLI command for the shared drive that you try to access. Select Start > Run and type Find Computer to try to locate the network resource. Double-click on the Network Neighborhood icon. Check that some or all network resources and PCs are shown. Verify that the PC that runs the VPN Client gets the correct WINS and Domain Name System (DNS) information. Select Start > Run and type ipconfig /all to see this information. Check event logs and debugs to see the WINS and DNS information that is passed down from the headend device to the remote VPN Client. If you use an LMHOSTS file, try to use NetBIOS names by issuing the nbtstat -c command. After an LMHOST file is loaded, the lifetime reads -1. Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, thank you for the reply, all these commands sound like troubleshot steps, do you mean once we figure out the root cause, the issue won’t happen again?